1. Home
  2. Vulnerabilities
  3. CVE-2025-38416
0.0
NA
CVE-2025-38416
Linux NFC NCI UART TTY Null Pointer Dereference
Description

In the Linux kernel, the following vulnerability has been resolved: NFC: nci: uart: Set tty->disc_data only in success path Setting tty->disc_data before opening the NCI device means we need to clean it up on error paths. This also opens some short window if device starts sending data, even before NCIUARTSETDRIVER IOCTL succeeded (broken hardware?). Close the window by exposing tty->disc_data only on the success path, when opening of the NCI device and try_module_get() succeeds. The code differs in error path in one aspect: tty->disc_data won't be ever assigned thus NULL-ified. This however should not be relevant difference, because of "tty->disc_data=NULL" in nci_uart_tty_open().

INFO

Published Date :

July 25, 2025, 2:15 p.m.

Last Modified :

July 25, 2025, 3:29 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2025-38416 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
Solution
This information is provided by the 3rd party feeds.
  • Upgrade the affs-modules-6.1.0-37-4kc-malta-di packages.
Public PoC/Exploit Available at Github

CVE-2025-38416 has a 1 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2025-38416.

URL Resource
https://git.kernel.org/stable/c/000bfbc6bc334a93fffca8f5aa9583e7b6356cb5
https://git.kernel.org/stable/c/55c3dbd8389636161090a2b2b6d2d709b9602e9c
https://git.kernel.org/stable/c/a514fca2b8e95838a3ba600f31a18fa60b76d893
https://git.kernel.org/stable/c/a8acc7080ad55c5402a1b818b3008998247dda87
https://git.kernel.org/stable/c/ac6992f72bd8e22679c1e147ac214de6a7093c23
https://git.kernel.org/stable/c/dc7722619a9c307e9938d735cf4a2210d3d48dcb
https://git.kernel.org/stable/c/e9799db771b2d574d5bf0dfb3177485e5f40d4d6
https://git.kernel.org/stable/c/fc27ab48904ceb7e4792f0c400f1ef175edf16fe
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2025-38416 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2025-38416 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Profile Photo
w4zu/Debian_security

DSA and DLA for Debian last 14 days

Python

Updated: 4 hours, 16 minutes ago
0 stars 0 fork 0 watcher
Born at : Feb. 12, 2025, 2:08 p.m. This repo has been linked 378 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2025-38416 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2025-38416 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jul. 25, 2025

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: NFC: nci: uart: Set tty->disc_data only in success path Setting tty->disc_data before opening the NCI device means we need to clean it up on error paths. This also opens some short window if device starts sending data, even before NCIUARTSETDRIVER IOCTL succeeded (broken hardware?). Close the window by exposing tty->disc_data only on the success path, when opening of the NCI device and try_module_get() succeeds. The code differs in error path in one aspect: tty->disc_data won't be ever assigned thus NULL-ified. This however should not be relevant difference, because of "tty->disc_data=NULL" in nci_uart_tty_open().
    Added Reference https://git.kernel.org/stable/c/000bfbc6bc334a93fffca8f5aa9583e7b6356cb5
    Added Reference https://git.kernel.org/stable/c/55c3dbd8389636161090a2b2b6d2d709b9602e9c
    Added Reference https://git.kernel.org/stable/c/a514fca2b8e95838a3ba600f31a18fa60b76d893
    Added Reference https://git.kernel.org/stable/c/a8acc7080ad55c5402a1b818b3008998247dda87
    Added Reference https://git.kernel.org/stable/c/ac6992f72bd8e22679c1e147ac214de6a7093c23
    Added Reference https://git.kernel.org/stable/c/dc7722619a9c307e9938d735cf4a2210d3d48dcb
    Added Reference https://git.kernel.org/stable/c/e9799db771b2d574d5bf0dfb3177485e5f40d4d6
    Added Reference https://git.kernel.org/stable/c/fc27ab48904ceb7e4792f0c400f1ef175edf16fe
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.